i think i’ve found the solution .

i just made a new ipxemenu entry with my winpe and force via API , the default parameter to 1 to this menu entry i can find in coreobjects pxemenuoptions.

i’ll keep you informed

@Redbob Any news on this?

@Sebastian-Roth

Well if they don’t match that may be part of the issue. The layout is from two identical Optiplex 7060 with 500GB drives. Top was one that imaged successfully, bottom is what I see when it doesn’t. All should match my golden image which is also an Optiplex 7060 with a 500 GB drive. I’m not sure where the disconnect would be from fogs settings, the image, and what ends up on the machine.

Again I’ve more or less gotten around this by modifying my image. So I figure if this issue is unique to me it’s probably safe to let it go. If it does start poking up from others at least my info would be a good starting point.

Sorry for the late reply… Tried on another computer, and I cannot get the FOG menu to appear (this computer has never registered on that FOG server).

@tcs_taylor this doesn’t sound like expected behavior. we’re probably going to need help from the other developers if we can confirm this bug. we’ll also need details on exactly what version of fog you’re running

@sebastian-roth said in Cant PXE Boot = PXE-T01: File not Found:

So here is another reason to push for the next release.

I think we are ready for another RC.

@rwakc well, it would be technically possible to set up a method where you could be automatically imaging any device pxe booted from the network, and set up multiple dhcp scopes on different network ports, serving out different pxe boot files with embedded scripts. that way, you’d be able to choose what image the system gets imaged with by choosing what network you plug the device into.

@JJ-Fullmer

:urls set msdart-url http://192.168.1.155/2-MSDART :MENU menu colour --rgb 0xff0000 0 || cpair --foreground 1 1 || cpair --foreground 0 3 || cpair --foreground 4 4 || item --gap -- ------------------------------------- item fog.local Boot from hard disk item msdart6x86 Microsoft DaRT for Windows Vista 32bit item msdart6x64 Microsoft DaRT for Windows Vista 64bit item msdart7x86 Microsoft DaRT for Windows 7 32bit item msdart7x64 Microsoft DaRT for Windows 7 64bit item msdart81x86 Microsoft DaRT for Windows 8.1 32bit item msdart81x64 Microsoft DaRT for Windows 8.1 64bit item fog.return Return to previous menu choose --default fog.local --timeout 5000000 target && goto ${target} :fog.local sanboot --no-describe --drive 0x80 || goto MENU :msdart6x86 initrd ${msdart-url}/MSDaRT60x86.iso chain memdisk iso raw :msdart6x64 initrd ${msdart-url}/MSDaRT60x64.iso chain memdisk iso raw :msdart7x86 initrd ${msdart-url}/MSDaRT70x86.iso chain memdisk iso raw :msdart7x64 initrd ${msdart-url}/MSDaRT70x64.iso chain memdisk iso raw :msdart81x86 initrd ${msdart-url}/MSDaRT8.1x86.iso chain memdisk iso raw :msdart81x64 initrd ${msdart-url}/MSDaRT8.1x64.iso chain memdisk iso raw :fog.return chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || prompt goto MENU

@Wayne-Workman i wasn’t really clever in browsing this forum with my phone, so I thought hey Google may just pop with the answer quicker but I will certainly use that link for my reference for future mishap.

Thanks bud (Y)

@monasmith529 said:

Yes it is a vm single nic vmxnet 3. No bridging.

No bridging??? Wouldn’t work I guess. Could you please explain a little more about your setup when asking a question next time. We cannot properly help you otherwise.

@Tom-Elliott said:

@Scott-B right but you don’t have anything in the advanced items. There is the login and it is working fine. But the advanced menu is its own configuration setting that you put your needs in.

Ah… okay. I thought that was just called from fog.advancedlogin.

Thank you for your reply. I will give it a shot.

Greg